Extending center cluster membership to additional compute resources

ABSTRACT

The present technology addresses a need to automatically configure a new compute resource to join an existing cluster of computing resources. The present technology provides a mechanism to ensure that the new compute resource is executing the same kernel version which further permits subsequent exchange at least one configuration message informing the new compute resource of necessary configuration parameters and an address to retrieve required software packages.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims the priority benefit of U.S. patent application No. 62/770,143, filed Nov. 20, 2018, entitled “EXTENDING CENTER CLUSTER MEMBERSHIP TO ADDITIONAL COMPUTE RESOURCES,” the disclosure of which is incorporated herein by reference.

TECHNICAL FIELD

The subject matter of this disclosure relates in general to technologies for improving the operation of a network, and more particularly, to improving addition of computing resources to an existing cluster of computing resources on the network.

BACKGROUND

A campus network can provide connectivity to computing devices (e.g., servers, workstations, desktop computers, laptop computers, tablets, mobile phones, etc.) and things (e.g., desk phones, security cameras, lighting, heating, ventilating, and air-conditioning (HVAC), windows, doors, locks, medical devices, industrial and manufacturing equipment, etc.) within environments such as offices, hospitals, colleges and universities, oil and gas facilities, factories, and similar locations. Some of the unique challenges a campus network may face include integrating wired and wireless devices, on-boarding computing devices and things that can appear anywhere in the network and maintaining connectivity when the devices and things migrate from location to location within the network, supporting bring your own device (BYOD) capabilities, connecting and powering Internet-of-Things (IoT) devices, and securing the network despite the vulnerabilities associated with Wi-Fi access, device mobility, BYOD, and IoT. Current approaches for deploying a network capable of providing these functions often require constant and extensive configuration and administration by highly skilled network engineers operating several different systems (e.g., directory-based identity services; authentication, authorization, and accounting (AAA) services, wireless local area network (WLAN) controllers; command line interfaces for each switch, router, or other network device of the network; etc.) and manually stitching these systems together. This can make network deployment difficult and time-consuming, and impede the ability of many organizations to innovate rapidly and to adopt new technologies, such as video, collaboration, and connected workspaces.

BRIEF DESCRIPTION OF THE FIGURES

To provide a complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an example of a physical topology of an enterprise network in accordance with an embodiment;

FIG. 2 illustrates an example of a logical architecture for an enterprise network in accordance with an embodiment;

FIGS. 3A-3I illustrate examples of graphical user interfaces for a network management system in accordance with an embodiment;

FIG. 4 illustrates an example of a physical topology for a multi-site enterprise network in accordance with an embodiment;

FIG. 5 illustrates a ladder diagram showing an example method in accordance with some embodiments of the present technology;

FIG. 6 illustrates an example of systems in accordance with some embodiments.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The detailed description set forth below is intended as a description of various configurations of embodiments and is not intended to represent the only configurations in which the subject matter of this disclosure can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject matter of this disclosure. However, it will be clear and apparent that the subject matter of this disclosure is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject matter of this disclosure.

Overview

The present technology provides for provisioning new resources to a computing cluster with minimal administrator involvement. While various provisioning and orchestration technologies might exist, they are prone to problems wherein new resources may be running incompatible, or non-ideal software of configurations for membership in a computing cluster, which leads to administrator time to troubleshoot and then ultimately install new software and reconfigure the cluster. The present technology provides for a mechanism whereby existing cluster members can inform a new computing resource of the appropriate configurations, and software versions required to participate in the cluster optimally. Furthermore, the existing cluster members can even provide the appropriate software packages, or a reference to acquire the appropriate software packages, in an executable format such that the new resource can automatically install the software and join the cluster and be fully and properly configured.

The present technology provides for sending, by a new computing resource, a request to join a computing cluster to at least one member of the computing cluster. The new computing resource can receive, in one or more communications, a reply from the member of the computing cluster that includes metadata describing requirements to join the computing cluster and describing a software bundle used by devices in the computing cluster. The new computing resource can download and install the software bundle, and then establish membership in the computing cluster.

The present technology can include a variety of system components including, among other potential components, a management cloud, an existing member of the cluster, a new resource to join the cluster, a software package repository, and a certificate authority. The existing member of the cluster is configured to receive a request for information needed to join the cluster of computing resources from a new computing resource, and in response, to send information describing protocols, identification of a software package, information for retrieving the software package, configuration parameters, and authentication information to the new computing resource.

The software package repository is configured to receive a request from the new computing resource and in response, to provide the software package to the new computing resource. Thereafter the new computing resource can receive the response from the software package repository and execute the software package, thereby configuring the new computing resource with all necessary software and configurations to join the cluster of computing resources.

The certificate authority is configured to receive a request to authenticate the new computing resource and to accept the new computing resource as a member of the cluster of computing resources, and in response, to accept the membership of the new computing resource

Example Embodiments

Intent-based networking is an approach for overcoming the deficiencies, discussed above and elsewhere in the present disclosure, of conventional enterprise networks. The motivation of intent-based networking is to enable a user to describe in plain language what he or she wants to accomplish (e.g., the user's intent) and have the network translate the user's objective into configuration and policy changes that are automatically propagated across a complex and heterogeneous computing environment. Thus, an intent-based network can abstract network complexity, automate much of the work of provisioning and managing the network typically handled by a network administrator, and assure secure operation and optimal performance of the network. As an intent-based network becomes aware of the users, devices, and things making connections in the network, it can automatically apply security permissions and service levels in accordance with the privileges and quality of experience (QoE) assigned to the users, devices, and things. Table 1 sets forth examples of intents and workflows that can be automated by an intent-based network to achieve the desired outcome.

TABLE 1 Examples of Intents and Associated Workflows Intent Workflow I need to scale out my Extend network segments; update load balancer configuration; application database configure quality of service (QoS) I have scheduled a Create high-definition (HD) video connection; prioritize with telemedicine session end-to-end QoS; validate performance; keep the communication at 10 am safe; tear down connection after call I am rolling out a new IoT Create a new segment for all factory devices to connect to the app for factory equipment IoT app; isolate from other traffic; apply service level agreement monitoring (SLA); validate SLA; optimize traffic flow I need to deploy a secure Provision multiple networks and subnets; configure access multi-tier application control lists (ACLs) and firewall rules; advertise routing information

FIG. 1 illustrates an example of a physical topology of an enterprise network 100 for providing intent-based networking. It should be understood that, for the enterprise network 100 and any network discussed herein, there can be additional or fewer nodes, devices, links, networks, or components in similar or alternative configurations. Example embodiments with different numbers and/or types of endpoints, nodes, cloud components, servers, software components, devices, virtual or physical resources, configurations, topologies, services, appliances, or deployments are also contemplated herein. Further, the enterprise network 100 can include any number or type of resources, which can be accessed and utilized by endpoints or network devices. The illustrations and examples provided herein are for clarity and simplicity.

In this example, the enterprise network 100 includes a management cloud 102 and a network fabric 120. Although shown as an external network or cloud to the network fabric 120 in this example, the management cloud 102 may alternatively or additionally reside on the premises of an organization or in a colocation center (in addition to being hosted by a cloud provider or similar environment). The management cloud 102 can provide a central management plane for building and operating the network fabric 120. The management cloud 102 can be responsible for forwarding configuration and policy distribution, as well as device management and analytics. The management cloud 102 can comprise one or more network controller appliances 104, one or more authentication, authorization, and accounting (AAA) appliances 106, one or more wireless local area network controllers (WLCs) 108, and one or more fabric control plane nodes 110. In other embodiments, one or more elements of the management cloud 102 may be co-located with the network fabric 120.

The network controller appliance(s) 104 can function as the command and control system for one or more network fabrics and can house automated workflows for deploying and managing the network fabric(s). The network controller appliance(s) 104 can include automation, design, policy, provisioning, and assurance capabilities, among others, as discussed further below with respect to FIG. 2. In some embodiments, one or more Cisco Digital Network Architecture (Cisco DNA™) appliances can operate as the network controller appliance(s) 104.

The AAA appliance(s) 106 can control access to computing resources, facilitate enforcement of network policies, audit usage, and provide information necessary to bill for services. The AAA appliance can interact with the network controller appliance(s) 104 and with databases and directories containing information for users, devices, things, policies, billing, and similar information to provide authentication, authorization, and accounting services. In some embodiments, the AAA appliance(s) 106 can utilize Remote Authentication Dial-In User Service (RADIUS) or Diameter to communicate with devices and applications. In some embodiments, one or more Cisco® Identity Services Engine (ISE) appliances can operate as the AAA appliance(s) 106.

The WLC(s) 108 can support fabric-enabled access points attached to the network fabric 120, handling traditional tasks associated with a WLC as well as interactions with the fabric control plane for wireless endpoint registration and roaming. In some embodiments, the network fabric 120 can implement a wireless deployment that moves data-plane termination (e.g., VXLAN) from a centralized location (e.g., with previous overlay Control and Provisioning of Wireless Access Points (CAPWAP) deployments) to an access point/fabric edge node. This can enable distributed forwarding and distributed policy application for wireless traffic while retaining the benefits of centralized provisioning and administration. In some embodiments, one or more Cisco® Wireless Controllers, Cisco® Wireless LAN, and/or other Cisco DNA™-ready wireless controllers can operate as the WLC(s) 108.

The network fabric 120 can comprise fabric border nodes 122A and 122B (collectively, 122), fabric intermediate nodes 124A-D (collectively, 124), and fabric edge nodes 126A-F (collectively, 126). Although the fabric control plane node(s) 110 are shown to be external to the network fabric 120 in this example, in other embodiments, the fabric control plane node(s) 110 may be co-located with the network fabric 120. In embodiments where the fabric control plane node(s) 110 are co-located with the network fabric 120, the fabric control plane node(s) 110 may comprise a dedicated node or set of nodes or the functionality of the fabric control node(s) 110 may be implemented by the fabric border nodes 122.

The fabric control plane node(s) 110 can serve as a central database for tracking all users, devices, and things as they attach to the network fabric 120, and as they roam around. The fabric control plane node(s) 110 can allow network infrastructure (e.g., switches, routers, WLCs, etc.) to query the database to determine the locations of users, devices, and things attached to the fabric instead of using a flood and learn mechanism. In this manner, the fabric control plane node(s) 110 can operate as a single source of truth about where every endpoint attached to the network fabric 120 is located at any point in time. In addition to tracking specific endpoints (e.g., /32 address for IPv4, /128 address for IPv6, etc.), the fabric control plane node(s) 110 can also track larger summarized routers (e.g., IP/mask). This flexibility can help in summarization across fabric sites and improve overall scalability.

The fabric border nodes 122 can connect the network fabric 120 to traditional Layer 3 networks (e.g., non-fabric networks) or to different fabric sites. The fabric border nodes 122 can also translate context (e.g., user, device, or thing mapping and identity) from one fabric site to another fabric site or to a traditional network. When the encapsulation is the same across different fabric sites, the translation of fabric context is generally mapped 1:1. The fabric border nodes 122 can also exchange reachability and policy information with fabric control plane nodes of different fabric sites. The fabric border nodes 122 also provide border functions for internal networks and external networks. Internal borders can advertise a defined set of known subnets, such as those leading to a group of branch sites or to a data center. External borders, on the other hand, can advertise unknown destinations (e.g., to the Internet similar in operation to the function of a default route).

The fabric intermediate nodes 124 can operate as pure Layer 3 forwarders that connect the fabric border nodes 122 to the fabric edge nodes 126 and provide the Layer 3 underlay for fabric overlay traffic.

The fabric edge nodes 126 can connect endpoints to the network fabric 120 and can encapsulate/decapsulate and forward traffic from these endpoints to and from the network fabric. The fabric edge nodes 126 may operate at the perimeter of the network fabric 120 and can be the first points for attachment of users, devices, and things and the implementation of policy. In some embodiments, the network fabric 120 can also include fabric extended nodes (not shown) for attaching downstream non-fabric Layer 2 network devices to the network fabric 120 and thereby extend the network fabric. For example, extended nodes can be small switches (e.g., compact switch, industrial Ethernet switch, building automation switch, etc.) which connect to the fabric edge nodes via Layer 2. Devices or things connected to the fabric extended nodes can use the fabric edge nodes 126 for communication to outside subnets.

In this example, the network fabric can represent a single fabric site deployment which can be differentiated from a multi-site fabric deployment as discussed further below with respect to FIG. 4.

In some embodiments, all subnets hosted in a fabric site can be provisioned across every fabric edge node 126 in that fabric site. For example, if the subnet 10.10.10.0/24 is provisioned in a given fabric site, this subnet may be defined across all of the fabric edge nodes 126 in that fabric site, and endpoints located in that subnet can be placed on any fabric edge node 126 in that fabric. This can simplify IP address management and allow deployment of fewer but larger subnets. In some embodiments, one or more Cisco® Catalyst switches, Cisco Nexus® switches, Cisco Meraki® MS switches, Cisco® Integrated Services Routers (ISRs), Cisco® Aggregation Services Routers (ASRs), Cisco® Enterprise Network Compute Systems (ENCS), Cisco® Cloud Service Virtual Routers (CSRvs), Cisco Integrated Services Virtual Routers (ISRvs), Cisco Meraki® MX appliances, and/or other Cisco DNA-Ready™ devices can operate as the fabric nodes 122, 124, and 126.

The enterprise network 100 can also include wired endpoints 130A, 130C, 130D, and 130F and wireless endpoints 130B and 130E (collectively, 130). The wired endpoints 130A, 130C, 130D, and 130F can connect by wire to fabric edge nodes 126A, 126C, 126D, and 126F, respectively, and the wireless endpoints 130B and 130E can connect wirelessly to wireless access points 128B and 128E (collectively, 128), respectively, which in turn can connect by wire to fabric edge nodes 126B and 126E, respectively. In some embodiments, Cisco Aironet® access points, Cisco Meraki® MR access points, and/or other Cisco DNA™-ready access points can operate as the wireless access points 128.

The endpoints 130 can include general purpose computing devices (e.g., servers, workstations, desktop computers, etc.), mobile computing devices (e.g., laptops, tablets, mobile phones, etc.), wearable devices (e.g., watches, glasses or other head-mounted displays (HMDs), ear devices, etc.), and so forth. The endpoints 130 can also include Internet of Things (IoT) devices or equipment, such as agricultural equipment (e.g., livestock tracking and management systems, watering devices, unmanned aerial vehicles (UAVs), etc.); connected cars and other vehicles; smart home sensors and devices (e.g., alarm systems, security cameras, lighting, appliances, media players, HVAC equipment, utility meters, windows, automatic doors, door bells, locks, etc.); office equipment (e.g., desktop phones, copiers, fax machines, etc.); healthcare devices (e.g., pacemakers, biometric sensors, medical equipment, etc.); industrial equipment (e.g., robots, factory machinery, construction equipment, industrial sensors, etc.); retail equipment (e.g., vending machines, point of sale (POS) devices, Radio Frequency Identification (RFID) tags, etc.); smart city devices (e.g., street lamps, parking meters, waste management sensors, etc.); transportation and logistical equipment (e.g., turnstiles, rental car trackers, navigational devices, inventory monitors, etc.); and so forth.

In some embodiments, the network fabric 120 can support wired and wireless access as part of a single integrated infrastructure such that connectivity, mobility, and policy enforcement behavior are similar or the same for both wired and wireless endpoints. This can bring a unified experience for users, devices, and things that are independent of the access media.

In integrated wired and wireless deployments, control plane integration can be achieved with the WLC(s) 108 notifying the fabric control plane node(s) 110 of joins, roams, and disconnects by the wireless endpoints 130 such that the fabric control plane node(s) can have connectivity information about both wired and wireless endpoints in the network fabric 120, and can serve as the single source of truth for endpoints connected to the network fabric. For data plane integration, the WLC(s) 108 can instruct the fabric wireless access points 128 to form a VXLAN overlay tunnel to their adjacent fabric edge nodes 126. The AP VXLAN tunnel can carry segmentation and policy information to and from the fabric edge nodes 126, allowing connectivity and functionality identical or similar to that of a wired endpoint. When the wireless endpoints 130 join the network fabric 120 via the fabric wireless access points 128, the WLC(s) 108 can onboard the endpoints into the network fabric 120 and inform the fabric control plane node(s) 110 of the endpoints' Media Access Control (MAC) addresses. The WLC(s) 108 can then instruct the fabric wireless access points 128 to form VXLAN overlay tunnels to the adjacent fabric edge nodes 126. Next, the wireless endpoints 130 can obtain IP addresses for themselves via Dynamic Host Configuration Protocol (DHCP). Once that completes, the fabric edge nodes 126 can register the IP addresses of the wireless endpoint 130 to the fabric control plane node(s) 110 to form a mapping between the endpoints' MAC and IP addresses, and traffic to and from the wireless endpoints 130 can begin to flow.

FIG. 2 illustrates an example of a logical architecture 200 for an enterprise network (e.g., the enterprise network 100). One of ordinary skill in the art will understand that, for the logical architecture 200 and any system discussed in the present disclosure, there can be additional or fewer components in similar or alternative configurations. The illustrations and examples provided in the present disclosure are for conciseness and clarity. Other embodiments may include different numbers and/or types of elements but one of ordinary skill the art will appreciate that such variations do not depart from the scope of the present disclosure. In this example, the logical architecture 200 includes a management layer 202, a controller layer 220, a network layer 230 (such as embodied by the network fabric 120), a physical layer 240 (such as embodied by the various elements of FIG. 1), and a shared services layer 250.

The management layer 202 can abstract the complexities and dependencies of other layers and provide a user with tools and workflows to manage an enterprise network (e.g., the enterprise network 100). The management layer 202 can include a user interface 204, design functions 206, policy functions 208, provisioning functions 210, assurance functions 212, platform functions 214, and base automation functions 216. The user interface 204 can provide a user with a single point to manage and automate the network. The user interface 204 can be implemented within a web application/web server accessible by a web browser and/or an application/application server accessible by a desktop application, a mobile app, a shell program or other command line interface (CLI), an Application Programming Interface (e.g., restful state transfer (REST), Simple Object Access Protocol (SOAP), Service Oriented Architecture (SOA), etc.), and/or another suitable interface in which the user can configure network infrastructure, devices, and things that are cloud-managed; provide user preferences; specify policies, enter data; review statistics; configure interactions or operations; and so forth. The user interface 204 may also provide visibility information, such as views of a network, network infrastructure, computing devices, and things. For example, the user interface 204 can provide a view of the status or conditions of the network, the operations taking place, services, performance, topology or layout, protocols implemented, running processes, errors, notifications, alerts, network structure, ongoing communications, data analysis, and so forth.

The design functions 206 can include tools and workflows for managing site profiles, maps, and floor plans, network settings, and IP address management, among others. The policy functions 208 can include tools and workflows for defining and managing network policies. The provisioning functions 210 can include tools and workflows for deploying the network. The assurance functions 212 can use machine learning and analytics to provide end-to-end visibility of the network by learning from the network infrastructure, endpoints, and other contextual sources of information. The platform functions 214 can include tools and workflows for integrating the network management system with other technologies. The base automation functions 216 can include tools and workflows to support the policy functions 208, the provisioning functions 210, the assurance functions 212, and the platform functions 214.

In some embodiments, the design functions 206, the policy functions 208, the provisioning functions 210, the assurance functions 212, the platform functions 214, and the base automation functions 216 can be implemented as microservices in which respective software functions are implemented in multiple containers communicating with each rather than amalgamating all tools and workflows into a single software binary. Each of the design functions 206, policy functions 208, provisioning functions 210, assurance functions 212, and platform functions 214 can be viewed as a set of related automation microservices to cover the design, policy authoring, provisioning, assurance, and cross-platform integration phases of the network lifecycle. The base automation functions 214 can support the top-level functions by allowing users to perform certain network-wide tasks.

FIGS. 3A-3I illustrate examples of graphical user interfaces for implementing the user interface 204. Although FIGS. 3A-3I show the graphical user interfaces as comprising web pages displayed in a browser executing on a large form-factor general purpose computing device (e.g., server, workstation, desktop, laptop, etc.), the principles disclosed in the present disclosure are widely applicable to client devices of other form factors, including tablet computers, smartphones, wearable devices, or other small form-factor general purpose computing devices; televisions; set-top boxes; IoT devices; and other electronic devices capable of connecting to a network and including input/output components to enable a user to interact with a network management system. One of ordinary skill will also understand that the graphical user interfaces of FIGS. 3A-3I are but one example of a user interface for managing a network. Other embodiments may include a fewer number or a greater number of elements.

FIG. 3A illustrates a graphical user interface 300A, which is an example of a landing screen or a home screen of the user interface 204. The graphical user interface 300A can include user interface elements for selecting the design functions 206, the policy functions 208, the provisioning functions 210, the assurance functions 212, and the platform functions 214. The graphical user interface 300A also includes user interface elements for selecting the base automation functions 216. In this example, the base automation functions 216 include:

-   -   A network discovery tool 302 for automating the discovery of         existing network elements to populate into inventory;     -   An inventory management tool 304 for managing the set of         physical and virtual network elements;     -   A topology tool 306 for visualizing the physical topology of         network elements;     -   An image repository tool 308 for managing software images for         network elements;     -   A command runner tool 310 for diagnosing one or more network         elements based on a CLI;     -   A license manager tool 312 for administering visualizing         software license usage in the network;     -   A template editor tool 314 for creating and authoring CLI         templates associated with network elements in a design profile;     -   A network PnP tool 316 for supporting the automated         configuration of network elements;     -   A telemetry tool 318 for designing a telemetry profile and         applying the telemetry profile to network elements; and     -   A data set and reports tool 320 for accessing various data sets,         scheduling data extracts, and generating reports in multiple         formats (e.g., Post Document Format (PDF), comma-separated         values (CSV), Tableau, etc.), such as an inventory data report,         a software image management (SWIM) server report, and a client         data report, among others.

FIG. 3B illustrates a graphical user interface 300B, an example of a landing screen for the design functions 206. The graphical user interface 300B can include user interface elements for various tools and workflows for logically defining an enterprise network. In this example, the design tools and workflows include:

-   -   A network hierarchy tool 322 for setting up the geographic         location, building, and floor plane details, and associating         these with a unique site id;     -   A network settings tool 324 for setting up network servers         (e.g., Domain Name System (DNS), DHCP, AAA, etc.), device         credentials, IP address pools, service provider profiles (e.g.,         QoS classes for a WAN provider), and wireless settings;     -   An image management tool 326 for managing software images and/or         maintenance updates, setting version compliance, and downloading         and deploying images;     -   A network profiles tool 328 for defining LAN, WAN, and WLAN         connection profiles (including Service Set Identifiers (SSIDs));         and     -   An authentication template tool 330 for defining modes of         authentication (e.g., closed authentication, Easy Connect, open         authentication, etc.).

The output of the design workflow 206 can include a hierarchical set of unique site identifiers that define the global and forwarding configuration parameters of the various sites of the network. The provisioning functions 210 may use the site identifiers to deploy the network.

FIG. 3C illustrates a graphical user interface 300C, an example of a landing screen for the policy functions 208. The graphical user interface 300C can include various tools and workflows for defining network policies. In this example, the policy design tools and workflows include:

-   -   A policy dashboard 332 for viewing virtual networks, group-based         access control policies, IP-based access control policies,         traffic copy policies, scalable groups, and IP network groups.         The policy dashboard 332 can also show the number of policies         that have failed to deploy. The policy dashboard 332 can provide         a list of policies and the following information about each         policy: policy name, policy type, policy version (e.g.,         iteration of policy which can be incremented each time the         policy changes, user who has modified the policy, description,         policy scope (e.g., user and device groups or applications that         the policy effects), and timestamp;     -   A group-based access control policies tool 334 for managing         group-based access controls or SGACLs. A group-based access         control policy can define scalable groups and an access contract         (e.g., rules that make up the access control policies, such as         to permit or deny when traffic matches on the policy);     -   An IP-based access control policies tool 336 for managing         IP-based access control policies. An IP-based access control can         define an IP network group (e.g., IP subnets that share same         access control requirements) and an access contract;     -   An application policies tool 338 for configuring QoS for         application traffic. An application policy can define         application sets (e.g., sets of applications that with similar         network traffic needs) and a site scope (e.g., the site to which         an application policy is defined);     -   A traffic copy policies tool 340 for setting up an Encapsulated         Remote Switched Port Analyzer (ERSPAN) configuration such that         network traffic flow between two entities is copied to a         specified destination for monitoring or troubleshooting. A         traffic copy policy can define the source and destination of the         traffic flow to copy and a traffic copy contract that specifies         the device and interface where the copy of traffic is sent; and     -   A virtual network policies tool 343 for segmenting the physical         network into multiple logical networks.

The output of the policy workflow 208 can include a set of virtual networks, security groups, and access and traffic policies that define the policy configuration parameters of the various sites of the network. The provisioning functions 210 may use virtual networks, groups, and policies for deployment in the network.

FIG. 3D illustrates a graphical user interface 300D, an example of a landing screen for the provisioning functions 210. The graphical user interface 300D can include various tools and workflows for deploying the network. In this example, the provisioning tools and workflows include:

-   -   A device provisioning tool 344 for assigning devices to the         inventory and deploying the required settings and policies, and         adding devices to sites; and     -   A fabric provisioning tool 346 for creating fabric domains and         adding devices to the fabric.

The output of the provisioning workflow 210 can include the deployment of the network underlay and fabric overlay, as well as policies (defined in the policy workflow 208).

FIG. 3E illustrates a graphical user interface 300E, an example of a landing screen for the assurance functions 212. The graphical user interface 300E can include various tools and workflows for managing the network. In this example, the assurance tools and workflows include:

-   -   A health overview tool 344 for providing a global view of the         enterprise network, including network infrastructure devices and         endpoints. The user interface element (e.g., drop-down menu, a         dialog box, etc.) associated with the health overview tool 344         can also be toggled to switch to additional or alternative         views, such as a view of the health of network infrastructure         devices alone, a view of the health of all wired and wireless         clients, and a view of the health of applications running in the         network as discussed further below with respect to FIGS. 3F-3H;     -   An assurance dashboard tool 346 for managing and creating custom         dashboards;     -   An issues tool 348 for displaying and troubleshooting network         issues; and     -   A sensor management tool 350 for managing sensor-driven tests.

The graphical user interface 300E can also include a location selection user interface element 352, a time period selection user interface element 354, and a view type user interface element 356. The location selection user interface element 354 can enable a user to view the overall health of specific sites (e.g., as defined via the network hierarchy tool 322) and/or network domains (e.g., LAN, WLAN, WAN, data center, etc.). The time period selection user interface element 356 can enable display of the overall health of the network over specific time periods (e.g., last 3 hours, last 24 hours, last 7 days, custom, etc.). The view type user interface element 355 can enable a user to toggle between a geographical map view of the sites of the network (not shown) or a hierarchical site/building view (as shown).

Within the hierarchical site/building view, rows can represent the network hierarchy (e.g., sites and buildings as defined by the network hierarchy tool 322); column 358 can indicate the number of healthy clients as a percentage; column 360 can indicate the health of wireless clients by a score (e.g., 1-10), color and/or descriptor (e.g., red or critical associated with a health score 1 to 3 indicating the clients have critical issues, orange or warning associated with a health score of 4 to 7 indicating warnings for the clients, green or no errors or warnings associated with a health score of 8 to 10, grey or no data available associated with a health score of null or 0), or other indicator; column 362 can indicate the health of wired clients by score, color, descriptor, and so forth; column 364 can include user interface elements for drilling down to the health of the clients associated with a hierarchical site/building; column 366 can indicate the number of healthy network infrastructure devices as a percentage; column 368 can indicate the health of access switches by score, color, descriptor, and so forth; column 370 can indicate the health of core switches by score, color, descriptor, and so forth; column 372 can indicate the health of distribution switches by score, color, descriptor, and so forth; column 374 can indicate the health of routers by score, color, descriptor, and so forth; column 376 can indicate the health of WLCs by score, color, descriptor, and so forth; column 378 can indicate the health of other network infrastructure devices by score, color, descriptor, and so forth; and column 380 can include user interface elements for drilling down to the health of the network infrastructure devices associated with a hierarchical site/building. In other embodiments, client devices may be grouped in other ways besides wired or wireless, such as by device type (e.g., desktop, laptop, mobile phone, IoT device or more specific type of IoT device, etc.), manufacturer, model, operating system, and so forth. Likewise, network infrastructure devices can also be grouped along these and other ways in additional embodiments.

The graphical user interface 300E can also include an overall health summary user interface element (e.g., a view, pane, tile, card, container, widget, dashlet, etc.) that includes a client health summary user interface element 384 indicating the number of healthy clients as a percentage, a color-coded trend chart 386 indicating that percentage over a specific time period (e.g., as selected by the time period selection user interface element 354), a user interface element 388 breaking down the number of healthy clients as a percentage by client type (e.g., wireless, wired), a network infrastructure health summary user interface element 390 indicating the number of health network infrastructure devices as a percentage, a color-coded trend chart 392 indicating that percentage over a specific time period, and a user interface element 394 breaking down the number of network infrastructure devices as a percentage by network infrastructure device type (e.g., core switch, access switch, distribution switch, etc.).

The graphical user interface 300E can also include an issues user interface element 396 listing issues, if any, that must be addressed. Issues can be sorted based on timestamp, severity, location, device type, and so forth. Each issue may be selected to drill down to view a more detailed view of the selected issue.

FIG. 3F illustrates a graphical user interface 300F, an example of a screen for an overview of the health of network infrastructure devices alone, which may be navigated to, for instance, by toggling the health overview tool 344. The graphical user interface 300F can include a timeline slider 398 for selecting a more granular time range than a time period selection user interface element (e.g., the time period selection user interface element 354). The graphical user interface 300F can also include similar information to that shown in the graphical user interface 300E, such as a user interface element comprising a hierarchical site/building view and/or geographical map view similar to that of the graphical user interface 300E (except providing information only for network infrastructure devices) (not shown here), the number of healthy network infrastructure devices as a percentage 390, the color-coded trend charts 392 indicating that percentage by device type, the breakdown of the number of healthy network infrastructure devices by device type 394, and so forth. In addition, the graphical user interface 300F can display a view of the health of network infrastructure devices by network topology (not shown). This view can be interactive, such as by enabling a user to zoom in or out, pan left or right, or rotate the topology (e.g., by 90 degrees).

In this example, the graphical user interface 300F also includes a color-coded trend chart 3002 showing the performance of the network infrastructure devices over a specific time period; network health by device type tabs including a system health chart 3004 providing system monitoring metrics (e.g., CPU utilization, memory utilization, temperature, etc.), a data plane connectivity chart 3006 providing data plane metrics, such as uplink availability and link errors, and a control plane connectivity chart 3008 providing control plane metrics for each device type; an AP analytics user interface element including an up and down color-coded chart 3010 that provides AP status information (e.g., the number of APs connected to the network, and the number of APs not connected to the network, etc.) and a top number N of APs by client count chart 3012 that provides information about the APs that have the highest number of clients; a network devices table 3014 enabling a user to filter (e.g., by device type, health, or custom filters), view, and export network device information. A detailed view of the health of each network infrastructure device can also be provided by selecting that network infrastructure device in the network devices table 3014.

FIG. 3G illustrates a graphical user interface 300G, an example of a screen for an overview of the health of client devices, which may be navigated to, for instance, by toggling the health overview tool 344. The graphical user interface 300G can include an SSID user interface selection element 3016 for viewing the health of wireless clients by all SSIDs or a specific SSID, a band frequency user interface selection element 3018 for viewing the health of wireless clients by all band frequencies or a specific band frequency (e.g., 2.4 GHz, 5 GHz, etc.), and a time slider 3020 that may operate similarly to the time slider 398.

The graphical user interface 300G can also include a client health summary user interface element that provides similar information to that shown in the graphical user interface 300E, such as the number of healthy clients as a percentage 384 and a color-coded trend chart 386 indicating that percentage over a specific time period for each grouping of client devices (e.g., wired/wireless, device type, manufacturer, model, operating system, etc.). In addition, the client health summary user interface element can include a color-coded donut chart that provides a count of poor (e.g., red and indicating a client health score of 1 to 3), fair (e.g., orange and indicating a client health score of 4 to 7), good (e.g., green and indicating a health score of 8 to 10), and inactive (e.g., grey and indicating a health score that is null or 0) client devices. The count of client devices associated with each color, health score, health descriptor, and so forth may be displayed by a selection gesture directed toward that color (e.g., tap, double tap, long press, hover, click, right-click, etc.).

The graphical user interface 300G can also include a number of other client health metric charts in all sites or a selected site over a specific time period, such as:

-   -   Client onboarding times 3024;     -   Received Signal Strength Indications (RSSIs) 3026;     -   Connectivity signal-to-noise ratios (SNRs) 3028;     -   Client counts per SSID 3030;     -   Client counts per band frequency 3032;     -   DNS requests and response counters (not shown); and     -   Connectivity physical link state information 3034 indicating the         distribution of wired client devices that had their physical         links up, down, and had errors.

In addition, the graphical user interface 300G can include a client devices table 3036 enabling a user to filter (e.g., by device type, health, data (e.g., onboarding time>threshold, association time>threshold, DHCP>threshold, AAA>threshold, RSSI>threshold, etc.), or custom filters), view, and export client device information (e.g., user identifier, hostname, MAC address, IP address, device type, last heard, location, VLAN identifier, SSID, overall health score, onboarding score, connection score, network infrastructure device to which the client device is connected, etc.). A detailed view of the health of each client device can also be provided by selecting that client device in the client devices table 3036.

FIG. 3H illustrates a graphical user interface 300H, an example of a screen for an overview of the health of applications, which may be navigated to, for instance, by the toggling the health overview tool 344. The graphical user interface 300H can include application health summary user interface element including a percentage 3038 of the number of healthy applications as a percentage, a health score 3040 for each application or type of application (e.g., business relevant, business irrelevant, default; HTTP, VoIP, chat, email, bulk transfer, multimedia/streaming, etc.) running in the network, a top number N of applications by usage chart 3042. The health score 3040 can be calculated based on an application's qualitative metrics, such as packet loss, network latency, and so forth.

In addition, the graphical user interface 300H can also include an applications table 3044 enabling a user to filter (e.g., by application name, domain name, health, usage, average throughput, traffic class, packet loss, network latency, application latency, custom filters, etc.), view, and export application information. A detailed view of the health of each application can also be provided by selecting that application in the applications table 3044.

FIG. 3I illustrates an example of a graphical user interface 300I, an example of a landing screen for the platform functions 210. The graphical user interface 300C can include various tools and workflows for integrating with other technology systems. In this example, the platform integration tools and workflows include:

-   -   A bundles tool 3046 for managing packages of domain-specific         APIs, workflows, and other features for network programming and         platform integration;     -   A developer toolkit 3048 for accessing an API catalog listing         the available APIs and methods (e.g., GET, PUT, POST, DELETE,         etc.), descriptions, runtime parameters, return codes, model         schemas, and so forth. In some embodiments, the developer         toolkit 3048 can also include a “Try It” button to permit a         developer to experiment with a particular API to better         understand its behavior;     -   A runtime dashboard 3050 for viewing and analyzing basic metrics         or API and integration flow usage;     -   A platform settings tool 3052 to view and set global or         bundle-specific settings that define integration destinations         and event consumption preferences; and     -   A notifications user interface element 3054 for presenting         notifications regarding the availability of software updates,         security threats, and so forth.

Returning to FIG. 2, the controller layer 220 can comprise subsystems for the management layer 220 and may include a network control platform 222, a network data platform 224, and AAA services 226. These controller subsystems can form an abstraction layer to hide the complexities and dependencies of managing many network elements and protocols.

The network control platform 222 can provide automation and orchestration services for the network layer 230 and the physical layer 240, and can include the settings, protocols, and tables to automate management of the network and physical layers. For example, the network control platform 222 can provide the design functions 206, and the provisioning functions 210. In addition, the network control platform 222 can include tools and workflows for discovering switches, routers, wireless controllers, and other network infrastructure devices (e.g., the network discovery tool 302); maintaining network and endpoint details, configurations, and software versions (e.g., the inventory management tool 304); Plug-and-Play (PnP) for automating deployment of network infrastructure (e.g., the network PnP tool 316), Path Trace for creating visual data paths to accelerate the troubleshooting of connectivity problems, Easy QoS for automating quality of service to prioritize applications across the network, and Enterprise Service Automation (ESA) for automating deployment of physical and virtual network services, among others. The network control platform 222 can communicate with network elements using Network Configuration (NETCONF)/Yet Another Next Generation (YANG), Simple Network Management Protocol (SNMP), Secure Shell (SSH)/Telnet, and so forth. In some embodiments, the Cisco® Network Control Platform (NCP) can operate as the network control platform 222

The network data platform 224 can provide for network data collection, analytics, and assurance, and may include the settings, protocols, and tables to monitor and analyze network infrastructure and endpoints connected to the network. The network data platform 224 can collect multiple types of information from network infrastructure devices, including Syslog, SNMP, NetFlow, Switched Port Analyzer (SPAN), and streaming telemetry, among others.

In some embodiments, one or more Cisco DNA™ Center appliances can provide the functionalities of the management layer 210, the network control platform 222, and the network data platform 224. The Cisco DNA™ Center appliances can support horizontal scalability by adding additional Cisco DNA™ Center nodes to an existing cluster; high availability for both hardware components and software packages; backup and store mechanisms to support disaster discovery scenarios; role-based access control mechanisms for differentiated access to users, devices, and things based on roles and scope; and programmable interfaces to enable integration with third-party vendors. The Cisco DNA™ Center appliances can also be cloud-tethered to provide for the upgrade of existing functions and additions of new packages and applications without having to download and install them manually.

The AAA services 226 can provide identity and policy services for the network layer 230 and physical layer 240, and may include the settings, protocols, and tables to support endpoint identification and policy enforcement services. The AAA services 226 can provide tools and workflows to manage virtual networks and security groups and to create group-based policies and contracts. The AAA services 226 can identify and profile network infrastructure devices and endpoints using AAA/RADIUS, 802.1X, MAC Authentication Bypass (MAB), web authentication, and EasyConnect, among others. The AAA services 226 can also collect and use contextual information from the network control platform 222, the network data platform 224, and the shared services 250, among others. In some embodiments, Cisco® ISE can provide the AAA services 226.

The network layer 230 can be conceptualized as a composition of two layers, an underlay 234 comprising physical and virtual network infrastructure (e.g., routers, switches, WLCs, etc.) and a Layer 3 routing protocol for forwarding traffic, and an overlay 232 comprising a virtual topology for logically connecting wired and wireless users, devices, and things and applying services and policies to these entities. Network elements of the underlay 234 can establish connectivity between each other, such as via Internet Protocol (IP). The underlay may use any topology and routing protocol.

In some embodiments, the network controller 104 can provide a local area network (LAN) automation service, such as implemented by Cisco DNA™ Center LAN Automation, to automatically discover, provision, and deploy network devices. Once discovered, the automated underlay provisioning service can leverage Plug and Play (PnP) to apply the required protocol and network address configurations to the physical network infrastructure. In some embodiments, the LAN automation service may implement the Intermediate System to Intermediate System (IS-IS) protocol. Some of the advantages of IS-IS include neighbor establishment without IP protocol dependencies, peering capability using loopback addresses, and agnostic treatment of IPv4, IPv6, and non-IP traffic.

The overlay 232 can be a logical, virtualized topology built on top of the physical underlay 234, and can include a fabric data plane, a fabric control plane, and a fabric policy plane. In some embodiments, the fabric data plane can be created via packet encapsulation using Virtual Extensible LAN (VXLAN) with Group Policy Option (GPO). Some of the advantages of VXLAN-GPO include its support for both Layer 2 and Layer 3 virtual topologies (overlays), and its ability to operate over any IP network with built-in network segmentation.

In some embodiments, the fabric control plane can implement Locator/ID Separation Protocol (LISP) for logically mapping and resolving users, devices, and things. LISP can simplify routing by removing the need for each router to process every possible IP destination address and route. LISP can achieve this by moving a remote destination to a centralized map database that allows each router to manage only its local routes and query the map system to locate destination endpoints.

The fabric policy plane is where intent can be translated into network policy. That is, the policy plane is where the network operator can instantiate logical network policy based on services offered by the network fabric 120, such as security segmentation services, quality of service (QoS), capture/copy services, application visibility services, and so forth.

Segmentation is a method or technology used to separate specific groups of users or devices from other groups for the purpose of reducing congestion, improving security, containing network problems, controlling access, and so forth. As discussed, the fabric data plane can implement VXLAN encapsulation to provide network segmentation by using the virtual network identifier (VNI) and Scalable Group Tag (SGT) fields in packet headers. The network fabric 120 can support both macro-segmentation and micro-segmentation. Macro-segmentation logically separates a network topology into smaller virtual networks by using a unique network identifier and separate forwarding tables. This can be instantiated as a virtual routing and forwarding (VRF) instance and referred to as a virtual network (VN). That is, a VN is a logical network instance within the network fabric 120 defined by a Layer 3 routing domain and can provide both Layer 2 and Layer 3 services (using the VXLAN VNI to provide both Layer 2 and Layer 3 segmentation). Micro-segmentation logically separates user or device groups within a VN, by enforcing source to destination access control permissions, such as by using access control lists (ACLs). A scalable group is a logical object identifier assigned to a group of users, devices, or things in the network fabric 120. It can be used as source and destination classifiers in Scalable Group ACLs (SGACLs). The SGT can be used to provide address-agnostic group-based policies.

In some embodiments, the fabric control plane node 110 may implement the Locator/Identifier Separation Protocol (LISP) to communicate with one another and with the management cloud 102. Thus, the control plane nodes may operate a host tracking database, a map server, and a map resolver. The host tracking database can track the endpoints 130 connected to the network fabric 120 and associate the endpoints to the fabric edge nodes 126, thereby decoupling an endpoint's identifier (e.g., IP or MAC address) from its location (e.g., closest router) in the network.

The physical layer 240 can comprise network infrastructure devices, such as switches and routers 110, 122, 124, and 126 and wireless elements 108 and 128 and network appliances, such as the network controller appliance(s) 104, and the AAA appliance(s) 106.

The shared services layer 250 can provide an interface to external network services, such as cloud services 252; Domain Name System (DNS), DHCP, IP Address Management (IPAM), and other network address management services 254; firewall services 256; Network as a Sensor (Naas)/Encrypted Threat Analytics (ETA) services; and Virtual Network Functions (VNFs) 260; among others. The management layer 202 and/or the controller layer 220 can share identity, policy, forwarding information, and so forth via the shared services layer 250 using APIs.

FIG. 4 illustrates an example of a physical topology for a multi-site enterprise network 400. In this example, the network fabric comprises fabric sites 420A and 420B. The fabric site 420A can include a fabric control node 410A, fabric border nodes 422A and 422B, fabric intermediate nodes 424A and 424B (shown here in dashed line and not connected to the fabric border nodes or the fabric edge nodes for simplicity), and fabric edge nodes 426A-D. The fabric site 420B can include a fabric control node 410B, fabric border nodes 422C-E, fabric intermediate nodes 424C and 424D, and fabric edge nodes 426D-F. Multiple fabric sites corresponding to a single fabric, such as the network fabric of FIG. 4, can be interconnected by a transit network. A transit network can be a portion of a network fabric that has its own control plane nodes and border nodes but does not have edge nodes. In addition, a transit network shares at least one border node with each fabric site that it interconnects.

In general, a transit network connects a network fabric to the external world. There are several approaches to external connectivity, such as a traditional IP network 436, traditional WAN 438A, Software-Defined WAN (SD-WAN) (not shown), or Software-Defined Access (SD-Access) 438B. Traffic across fabric sites, and to other types of sites, can use the control plane and data plane of the transit network to provide connectivity between these sites. A local border node can operate as the handoff point from the fabric site, and the transit network can deliver traffic to other sites. The transit network may use additional features. For example, if the transit network is a WAN, then features like performance routing may also be used. To provide end-to-end policy and segmentation, the transit network should be cable of carrying endpoint context information (e.g., VRF, SGT) across the network. Otherwise, a re-classification of the traffic may be needed at the destination site border.

The local control plane in a fabric site may only hold state relevant to endpoints that are connected to edge nodes within the local fabric site. The local control plane can register local endpoints via local edge nodes, as with a single fabric site (e.g., the network fabric 120). An endpoint that isn't explicitly registered with the local control plane may be assumed to be reachable via border nodes connected to the transit network. In some embodiments, the local control plane may not hold state for endpoints attached to other fabric sites such that the border nodes do not register information from the transit network. In this manner, the local control plane can be independent of other fabric sites, thus enhancing the overall scalability of the network.

The control plane in the transit network can hold summary state for all fabric sites that it interconnects. This information can be registered to the transit control plane by border nodes from different fabric sites. The border nodes can register EID information from the local fabric site into the transit network control plane for summary EIDs only and thus further improve scalability.

The multi-site enterprise network 400 can also include a shared services cloud 432. The shared services cloud 432 can comprise one or more network controller appliances 404, one or more AAA appliances 406, and other shared servers (e.g., DNS; DHCP; IPAM; SNMP and other monitoring tools; NetFlow, Syslog, and other data collectors, etc.) may reside. These shared services can generally reside outside of the network fabric and in a global routing table (GRT) of an existing network. In this case, some method of inter-VRF routing may be required. One option for inter-VRF routing is to use a fusion router, which can be an external router that performs inter-VRF leaking (e.g., import/export of VRF routes) to fuse the VRFs together. Multi-Protocol can be used for this route exchange since it can inherently prevent routing loops (e.g., using the AS_PATH attribute). Other routing protocols can also be used but may require complex distribute-lists and prefix-lists to prevent loops.

However, there can be several disadvantages in using a fusion router to achieve inter-VN communication, such as route duplication because routes leaked from one VRF to another are programmed in hardware tables and can result in more TCAM utilization, manual configuration at multiple touch points wherever route-leaking is implemented, loss of SGT context because SGTs may not be maintained across VRFs and must be re-classified once the traffic enters the other VRF, and traffic hairpinning because traffic may need to be routed to the fusion router, and then back to the fabric border node.

SD-Access Extranet can provide a flexible and scalable method for achieving inter-VN communications by avoiding route duplication because inter-VN lookup occurs in the fabric control plane (e.g., software) such that route entries do not need to be duplicated in hardware; providing a single touchpoint because the network management system (e.g., Cisco DNA™ Center) can automate the inter-VN lookup policy, making it a single point of management; maintaining SGT context because the inter-VN lookup occurs in the control plane node(s) (e.g., software), and avoids hair-pinning because inter-VN forwarding can occur at the fabric edge (e.g., the same intra-VN) so traffic does not need to hairpin at the border node. Another advantage is that a separate VN can be made for each of the common resources that are needed (e.g., a Shared Services VN, an Internet VN, a data center VN, etc.).

Extending Center Cluster Membership to Additional Compute Resources

The systems described above in FIG. 1-FIG. 4 are useful for managing an enterprise network. As referenced above, one aspect of managing an enterprise network involves adding additional compute resources such as network controller appliances 104, authentication, authorization, and accounting (AAA) appliances 106, wireless local area network controllers (WLCs) 108, fabric control plane nodes 110, border nodes 122, intermediate nodes 124, edge nodes 126, access points 128, and end points 130. In some embodiments, these compute resources can make up a cluster which is made up of multiple independent computing entities that cooperates with each other to achieve the same computational goal.

Entities within a cluster use some previously agreed protocol to coordinate with each other. However, an entity that is to become a new member of a cluster may have a different version of software or a protocol which may be incompatible with that which is currently used in the cluster. When this happens, the new member will not be able to join the cluster and acquire membership. Often such a problem requires a software or configuration modification prior to joining the cluster. Currently, this process can require administrator intervention, and delays cluster formation.

In some embodiments, the present technology can communicate appropriate software and configuration requirements to an entity attempting to become a new member of a cluster (or to update existing members within the cluster) by transferring a manifest file that contains necessary information regarding appropriate software needed to join the cluster, where to download the software, and appropriate configurations.

FIG. 5 illustrates an example ladder diagram showing example communications and a method used to add compute resources to an existing cluster of computing resources. The computing resources can be any computing resource whether physical or virtual and can provide any function including networking, indexing, and storage, or computational type tasks.

The present technology can address the above problems by utilizing provisioning function 210 of management cloud 102 to configure multiple levels of the network (illustrated in FIG. 2) to be able to automatically configure and accept a new compute resource into the cluster.

Prior to the first communication in the method illustrated in FIG. 5, a first resource needs to be provisioned. Provisioning function 210 can configure the first resource to provide a function, and the first resource can thereafter be used (as illustrated in FIG. 5) to configure every additional resource joining the first resource in a cluster to provide the function. Provisioning function 210 can be used at the direction of a network administrator, or other functions of management cloud 102 to configure the first resource. Configuring the first resource can include defining an appropriate software package, including a run time environment, versions, APIs, network configurations, etc. Whenever a resource is provisioned, the resource will generate and store a bundle including a Docker image (or another type of container) containing the software package and will create a manifest including information regarding the software release versions, configuration settings, and other data necessary for the appropriate configuration. In some embodiments, the bundle can be stored directly on the first resource, or it can be stored or managed by image repository 308.

Once the first resource has been configured, it can be used by newly joining resources, as outlined in FIG. 5, to ensure that every member of a cluster is configured in the same way.

FIG. 5 illustrates a method 500 by which a new computing resource 502 can join a cluster through communication with an existing cluster member 501 (a previously configured resource) of the cluster and other management cloud 102 resources.

Method 500 can begin when the new computing resource 502 initializes 510 and executes firmware effective to run a preboot execution environment protocol wherein new computing resource 502 sends a preboot execution environment (PXE) request 511 to a preboot execution environment server which receives the request. In response, the preboot execution environment server sends a boot image including software kernel defining the operating environment used by the existing cluster member(s) 501 to the new resource 502 joining the cluster to initialize the new resource 502 joining the cluster.

The new computing resource 502 can receive the boot image and initialize 513 using the boot image. These steps ensure that the new computing resource 502 is running the proper kernel.

In some embodiments, steps 511, 512, and 513 are optional as indicated by the dashed lines. In some embodiments, the new computing resource 502 is already running the proper kernel and steps 511, 512, and 513 can be skipped. In some embodiments, the new resource 502 joining the cluster simply does not perform steps 511, 512, and 513. In some embodiments, the preboot execution environment boot fails and therefore either does not perform steps 511, 512, and 513, or the effect of performing the steps is the same as if they have not been performed. These steps are optional because all resources will already include a Linux or Windows kernel and any software necessary to utilize a manifest, described below. The Linux kernel is natively able to execute a Docker container, and resources running the Windows kernel under the control of the management cloud 102 include additional software needed to execute a Docker container. As will be described below, the software in the Docker container is able to otherwise update the new resource 502 to be able to join the cluster.

Whether or not, the new computing resource 502 has performed the preboot execution environment boot 513, new computing resource 502 can request 517 a manifest from an existing cluster member 501. In order to know where to send request 517, new computing resource 502 can receive a communication from management cloud 102 directing the new computing resource 502 to join an existing cluster. The communication from management cloud 102 can provide instructions to make the manifest request 517 and direct it to one or more existing cluster members 501. In some embodiments, the new resource 502 might prompt the user through the management cloud 102 to provide an IP address of a member of the existing cluster to which the new resource 502 is to join.

An existing member 501 of the cluster can receive the manifest request 517 and either redirect the request to another existing member 501 of the cluster that has been designated for handling such requests, or it can respond. In response to the receiving the request, the existing cluster member 501 can send 518 the requested manifest including information describing protocols, APIs, versions, identification of a software package(s), information (a pointer) for retrieving the software package, configuration parameters, file format information, path information, data schemas, etc. In addition to the information in the manifest, the existing member 501 of the cluster can send a seed package for a certificate authority (e.g., public and private keys) that will be used as a basis of mutual trust between the new computing resource 502 and the existing cluster member(s) 501 in the cluster going forward.

In some embodiments, the manifest request 517 can include information about the existing software environment and configuration the new resource 502 is currently running, and the existing cluster member 501 can determine that the new computing resource is not running the same version of the software bundle as the existing cluster member 501. In some embodiments, the existing cluster member 501 can determine the differences between the existing software environment and configuration of the new member 502 compared to the existing cluster member 501. In such embodiments, the existing cluster member 501 can prepare a manifest that identifies the differences in configurations.

In some embodiments, the manifest request can include instructions to the new entity 502 joining to request and receive the Docker image from a docket daemon. In some embodiments, the existing cluster member 501 can send a Docker image containing software package(s) needed for participation in the cluster.

After receipt of the manifest, new computing resource 502 can process 519 the manifest data and install authentication information, such as software required for a distributed certificate authority. In some embodiments, authentication services such as the distributed certificate authority can be provided by AAA Service 226 of the management cloud 102.

As directed by the manifest, the new computing resource 502 can then request 522 the software package, and the request can be received 522 by a software package repository. In response, the software package repository can provide the software package to the new computing resource 502, which can run the software package 523. Examples of a software package include, but are not limited to executable Docker containers, Java executable, etc.

In some embodiments, the software package is a Docker image. The Docker image contains the following software to install: kernel loadable modules, Deb, apk, pip, or whl packages, golang dependent packages, java software (including jars), new libraries/binaries, new ansible orchestrations playbooks, new configuration files, etc. When this Docker image is run to completion, it ensures the new cluster member is running all identical software versions, and they are configured in a compatible way.

To facilitate such a Docker image to be available on the cluster, whenever a cluster software version is updated, it is required to generate a bundle as a part of the upgrade package that contains all the software updated into a Docker image and tagged with the release version. This image will be downloaded by a cluster member whenever a software update of the cluster is initiated. That way if a cluster keeps moving from a software version to another, a new member will always receive whatever latest version the cluster is running, and will be upgraded later along with the rest of the members of the cluster. That way all members of a cluster are guaranteed to run the identical version of cluster software.

Now that the new computing resource 502 has all of the necessary software and configurations to be a part of the clusters, the new computing resource 502 can attempt to join the cluster 526 by requesting its membership to be authenticated 527 by a certificate authority. The certificate authority can receive the request 527 to authenticate the new computing resource and to accept the new computing resource as a member of the cluster of computing resources, and in response 528, the certificate authority can accept the membership of the new computing resource. In some embodiments, the certificate authority can be distributed.

While the present technology has been primarily discussed in the context of the systems shown herein, such as shown in FIG. 1-FIG. 5 that is designed to manage an enterprise network, the present technology is applicable to any system in which expanding cluster membership is desired. Any system wherein current cluster members, or an orchestration service, can send a manifest that includes all information necessary for a new resource to automatically download and install necessary software versions, set up the proper configurations, and learn the proper authentication to join the cluster is contemplated by the present technology.

FIG. 6 shows an example of computing system 600, which can be for example any computing device making up network controller appliances 104, authentication, authorization, and accounting (AAA) appliances 106, wireless local area network controllers (WLCs) 108, fabric control plane nodes 110, border nodes 122, intermediate nodes 124, edge nodes 126, access points 128, end points 130, or management cloud 102 or any component thereof in which the components of the system are in communication with each other using connection 605. Connection 605 can be a physical connection via a bus, or a direct connection into processor 610, such as in a chipset architecture. Connection 605 can also be a virtual connection, networked connection, or logical connection.

In some embodiments, computing system 600 is a distributed system in which the functions described in this disclosure can be distributed within a datacenter, multiple datacenters, a peer network, etc. In some embodiments, one or more of the described system components represents many such components each performing some or all of the function for which the component is described. In some embodiments, the components can be physical or virtual devices.

Example system 600 includes at least one processing unit (CPU or processor) 610 and connection 605 that couples various system components including system memory 615, such as read-only memory (ROM) 620 and random access memory (RAM) 625 to processor 610. Computing system 600 can include a cache of high-speed memory 612 connected directly with, in close proximity to, or integrated as part of processor 610.

Processor 610 can include any general purpose processor and a hardware service or software service, such as services 632, 634, and 636 stored in storage device 630, configured to control processor 610 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Processor 610 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction, computing system 600 includes an input device 645, which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. Computing system 600 can also include output device 635, which can be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input/output to communicate with computing system 600. Computing system 600 can include communications interface 640, which can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement, and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

Storage device 630 can be a non-volatile memory device and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs), read-only memory (ROM), and/or some combination of these devices.

The storage device 630 can include software services, servers, services, etc., that when the code that defines such software is executed by the processor 610, it causes the system to perform a function. In some embodiments, a hardware service that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 610, connection 605, output device 635, etc., to carry out the function.

For clarity of explanation, in some instances, the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.

Any of the steps, operations, functions, or processes described herein may be performed or implemented by a combination of hardware and software services or services, alone or in combination with other devices. In some embodiments, a service can be software that resides in memory of a client device and/or one or more servers of a content management system and perform one or more functions when a processor executes the software associated with the service. In some embodiments, a service is a program, or a collection of programs that carry out a specific function. In some embodiments, a service can be considered a server. The memory can be a non-transitory computer-readable medium.

In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, solid state memory devices, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include servers, laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.

Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims. 

1. A computer-implemented method comprising: sending, by a new computing resource, a request to join a computing cluster including at least one member; receiving, in one or more communications, a reply including metadata describing requirements to join the computing cluster and a reference to a software bundle used by devices in the computing cluster; installing the software bundle; and establishing membership in the computing cluster.
 2. The computer-implemented method of claim 1, wherein the request to join the cluster is a request to the at least one member of the computing cluster for the metadata describing requirements to join the computing cluster.
 3. The computer-implemented method of claim 1, wherein the receiving of the reply including the reference to the software bundle is a result of a determination made by a member of the computing cluster that the new computing resource is not running the same version of the software bundle as the at least one member of the computing cluster.
 4. The computer-implemented method of claim 1, comprising: prior to the sending of the request to join the computing cluster, sending a preboot executing environment request; receiving a boot image in response to the preboot execution environment request; and initializing, by the new computing resource, using the received boot image.
 5. The computer-implemented method of claim 1, wherein the metadata describing requirements to join the computing cluster includes membership authentication information, the method comprising: authenticating, by the new computing resource, using the membership authentication information prior to the establishing membership in the cluster.
 6. The computer-implemented method of claim 1, wherein the software bundle is contained in a Docker container that is executable by the new computing resource.
 7. The computer-implemented method of claim 2, comprising: installing a software or configuration update by the at least one member of the computing cluster; and generating the software bundle containing the software or configuration included in the update and labeling the software bundle with a release version.
 8. A distributed computing management system for managing a cluster of computing resources comprising: an existing member of the cluster of computing resources to receive a request for information needed to join the cluster of computing resources from a new computing resource, and in response, to send information describing protocols, identification of a software package, information for retrieving the software package, configuration parameters, and authentication information to the new computing resource; and a software package repository to receive a request from the new computing resource and in response to provide the software package to the new computing resource.
 9. The distributed computing management system of claim 8 comprising: the new computing resource to receive the response from the software package repository and to execute the software package, thereby configuring the new computing resource with all necessary software and configurations to join the cluster of computing resources.
 10. The distributed computing management system of claim 8, wherein the software package is a Docker container.
 11. The distributed computing management system of claim 8, comprising: a certificate authority to receive a request to authenticate the new computing resource and to accept the new computing resource as a member of the cluster of computing resources, and in response, to accept the new computing resource as a member of the cluster.
 12. The distributed computing management system of claim 8, comprising: a preboot execution environment server to receive a preboot execution environment request from the new computing resource that is not part of the cluster of computing resources, and to send a boot image used by the cluster of computing resources to the new computing resource to initialize the new computing resource.
 13. The distributed computing management system of claim 8, wherein the existing member of the cluster of computing resources is configured to install a software or configuration update, and generate the software package containing the software or configuration included in the update and labeling the software package with a release version.
 14. A non-transitory computer-readable medium comprising instructions stored thereon that when executed are effective to cause one or more processors of a management cloud system to: send, by a new computing resource, a request to join an existing computing cluster including at least one member; receive, in one or more communications, a reply including metadata describing requirements to join the computing cluster and a reference to a software bundle used by devices in the computing cluster; install the software bundle; and establish membership in the computing cluster.
 15. The non-transitory computer-readable medium of claim 14, wherein the request to join the cluster is a request to the at least one member of the computing cluster for the metadata describing requirements to join the existing computing cluster.
 16. The non-transitory computer-readable medium of claim 14, wherein the receiving of the reply including the reference to the software bundle is a result of a determination made by a member of the existing computing cluster that the new computing resource is not running the same version of the software bundle as the at least one current member of the existing computing cluster.
 17. The non-transitory computer-readable medium of claim 14, wherein the instructions are effective to cause one or more processors of the management cloud system to: send a preboot executing environment request prior to the sending of the request to join the existing computing cluster; receive a boot image in response to the preboot execution environment request; and initialize, by the new computing resource, using the received boot image.
 18. The non-transitory computer-readable medium of claim 14, wherein the metadata describing requirements to join the existing computing cluster includes membership authentication information, wherein the instructions are effective to cause one or more processors of the management cloud system to: authenticate, by the new computing resource, using the membership authentication information prior to the establishing membership in the existing cluster.
 19. The non-transitory computer-readable medium of claim 14, wherein the software bundle is contained in a Docker container that is executable by the new computing resource.
 20. The non-transitory computer-readable medium of claim 15, wherein the instructions are effective to cause one or more processors of the management cloud system to: installing a software or configuration update by the at least one member of the computing cluster; and generating the software bundle containing the software or configuration included in the update and labeling the software bundle with a release version. 